Method and system for dynamically protecting a computer system from attack

ABSTRACT

A dynamic protection system can analyze a computer system to determine its vulnerabilities to attack and generate a policy for protecting the computer system based on the identified vulnerabilities. Data received by the computer system can be analyzed to determine if it poses a threat to the system. This can prevent the data from entering the system or host based on a determination that the data poses a threat. Also, the dynamic protection system can receive policy updates to allow it to protect the system more efficiently and effectively. In other words, the dynamic protection system can protect an evolving computer system operating in an environment that is characterized by constantly changing methods of attack. Furthermore, by minimizing a need for manual intervention, attacks can be rapidly and accurately detected with a minimization of false positives, thereby lowering the cost of operation.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority under 35 U.S.C. §120 to U.S. patent application Ser. No. 10/400,938 filed Mar. 27, 2003, titled, “Method and System for Dynamically Protecting a Computer System from Attack” now U.S. Pat. No. 7,913,303, and also claims priority under 35 U.S.C. §119 to U.S. Provisional Patent Application No. 60/441,422, titled Dynamic Threat Protection, filed Jan. 21, 2003. The complete disclosure of each of the above-identified applications is hereby fully incorporated herein by reference.

TECHNICAL FIELD

The present invention relates to the security of computer systems. More particularly, the present invention relates to a method and system for receiving a set of data, determining if the data should be blocked from the computer system, and selecting a method for blocking the data from the system.

BACKGROUND

As e-commerce, or doing business over the Internet, becomes a way of life rather than being characterized as novel commercial activity, protecting computer systems against malicious attacks or alleged pranks becomes vital to both businesses and individuals because of potential economic disasters. In other words, because businesses and individuals are becoming more and more dependent upon computer systems that are integrated with the Internet, any interruptions in service or attacks on such computer systems could have devastating financial repercussions.

Attacks on computer systems that are integrated with the Internet typically include computer viruses, worms or Trojan horses. A computer virus is a broad term for a program that replicates itself. A virus can cause many different types of damage, such as deleting data files, erasing programs, or destroying everything found on a computer hard drive. Not every virus can cause damage; some viruses simply flash annoying messages on a computer screen. A virus can be received by downloading files from the Internet to a personal computer or through electronic mail.

Worms are programs designed to infect networks, such as the Internet. A worm travels from network to network replicating itself along the way. Trojan horses pretend to be a program that the user wishes to launch. A Trojan horse can be a program or file that disguises itself as normal, helpful programs or files, but in fact are viruses.

In addition to the above types of attacks, other computer incidents can include attacks against an Internet service provider (“ISP”) or any computer connected to the Internet. One of the most common attacks against an ISP or any computer connected to the Internet is called a Smurf attack. In a Smurf attack, a target, such as an ISP or a computer connected to the Internet, is flooded with many “garbage” packets so that all of the target's available bandwidth is used up and the target or customers of the target or both cannot send or receive data by using e-mail, browsing the web, or any other Internet service.

As noted above, the nature of a distributed network, such as the Internet, makes it vulnerable to attack. The Internet was designed to allow for the freest possible exchange of information, data, and files. However, this free exchange of information carries a price: some users will try to attack the Internet and computers connected to the Internet; others will try to invade other users' privacy and attempt to crack databases of sensitive information or snoop around for information as it travels across Internet routes.

Two conventional methods exist for protecting computer systems from attack. One is a static method, which forces customers to upgrade or add new software to the system as time passes. These upgrades are called patches and they repair flaws in the software which previously allowed attacks to enter the system. The second method is intercept call hooking, which provides localized protection from some attacks that are not known about in advance by looking for abnormal procedure calls at a computer in the system. However, both methods can stop functional software from functioning due to false positive determinations of an attack on the system. While prior intrusion detection systems (“IDS”) can detect attacks or make changes to security configurations of network computers and systems, these conventional systems do not have the capability to rapidly update the protection systems.

Accordingly, there is a need in the art for dynamically protecting a computer system from attacks via the Internet. That is, there is a need for a method and system for blocking attacks only against the components and hosts in the system which are vulnerable to such an attack. Furthermore, there is a need for correlating suspicious data packets received by a computer system against hosts or workstations that may be vulnerable to a particular type of attack to support the blocking of data packets for only the vulnerable hosts. A need also exists for a method and system capable of being updated with new attack nomenclature without having to modify files currently located on the system. Finally, a need exists for a method to quickly update a dynamic protection system to address attacks having catastrophic effects on the computer system.

SUMMARY

A dynamic protection system (“DPS”) provides real-time protection for computer systems, networks, and hosts from attacks via a distributed computer network, such as the Internet. For one aspect of the present invention, DPS can receive a data packet and determine whether to block the packet from passing into the system, network, or host. If the decision is made to block the packet, DPS can determine how to block the packet. DPS typically initiates one or more blocking methods, including active blocking and passive blocking.

Passive blocking typically occurs at the system and network levels. To passively block the data packet, the DPS can send a reset packet to the intruder, the party sending the packet, or the party to whom the packet was sent. The reset packet tells the party receiving it that the connection has been severed.

Active blocking typically occurs at the host and in-line networking levels. To actively block the data packet, the DPS retrieves information about the intruder or receiving party. The retrieved information can include a network address, an internet protocol port, a protocol code, or a protocol type. DPS can add the retrieved information to a blocking instruction, and apply the instruction to the data packet. The instruction can prevent this and subsequent data packets, having the same or similar characteristics as the retrieved information, from entering the system, network or host.

For another aspect of the present invention, DPS can generate a policy to protect a computing system. The policy typically contains a series of instructions which can be used by network and host sensors to identify packets of data that should be blocked to protect the computer system from an attack. The policy can be generated by assessing the system for vulnerabilities and creating a report detailing these vulnerabilities for the resources of the computer system. The policy can then be used by one or more sensors to assist in the evaluation of data packets for possible attacks on the system, network, or host.

A central source also can transmit a new policy to the computer system in the form of a “virtual” patch on a regular basis to update the scope of attack protection for the computer system. Rather than modify the current protection software running on the system, the virtual patch typically adds new protection software to assist the system in protecting itself from previously known and unknown types of attacks. An attack is “unknown” if a policy for preventing the attack has not been generated by or received at the system, network, or host at the time the attack occurs or the new policy is received.

BRIEF DESCRIPTION OF DRAWINGS

For a more complete understanding of exemplary embodiments of the present invention and the advantages thereof, reference is now made to the following description in conjunction with the accompanying drawings in which:

FIG. 1 is a block diagram of a system level dynamic protection system constructed in accordance with an exemplary embodiment of the present invention;

FIG. 2 is a block diagram of a host level dynamic protection system constructed in accordance with an exemplary embodiment of the present invention;

FIG. 3 is a flowchart illustrating a process for dynamically protecting a system in accordance with an exemplary embodiment of the present invention;

FIG. 4 is a flowchart illustrating a process for generating a system level policy to dynamically protect the system in accordance with an exemplary embodiment of the present invention;

FIG. 5 is a flowchart illustrating a process for determining if a packet of data contains a suspicious event in accordance with an exemplary embodiment of the present invention;

FIG. 6 is a flowchart illustrating a passive process for blocking the packet of data in accordance with an exemplary embodiment of the present invention;

FIG. 7 is a flowchart illustrating an active process for blocking the packet of data in accordance with an exemplary embodiment of the present invention;

FIG. 8 is a flowchart illustrating an alternative active process for blocking a packet of data in accordance with an exemplary embodiment of the present invention;

FIG. 9 is a flowchart illustrating a process for dynamically protecting a host in accordance with an exemplary embodiment of the present invention;

FIG. 10 is a flowchart illustrating a process for evaluating a packet at the host in accordance with an exemplary embodiment of the present invention;

FIG. 11 is a flowchart illustrating a process for dynamically protecting a network in accordance with an exemplary embodiment of the present invention; and

FIG. 12 is a flowchart illustrating a process for updating a protection policy in accordance with an exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

The present invention supports a computer-implemented method and system for dynamically protecting an online operation from attacks against its system, network and hosts. Exemplary embodiments of the invention can be more readily understood by reference to the accompanying figures.

Although exemplary embodiments of the present invention will be generally described in the context of program and hardware modules operating on a host, network, and system, those skilled in the art will recognize that the present invention can also be implemented in conjunction with other program modules for other types of hosts, networks and systems. Furthermore, those skilled in the art will recognize that the present invention may be implemented in a stand-alone or in a distributed computing environment. In a distributed computing environment, program and hardware modules may be physically located in different local and remote memory storage devices. Examples of such distributed computing environments include local area networks of an office, enterprise-wide computer networks, and the global Internet.

Exemplary embodiments of the present invention include a computer program which embodies the functions described herein and illustrated in the appended flowcharts. However, it should be apparent that there could be many different ways of implementing the invention in computer programming, and the invention should not be construed as limited to any one set of computer program instructions. Further, a skilled programmer would be able to write such a computer program to implement the disclosed invention without difficulty based on the flowcharts and associated description in the application text, for example. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use the present invention. The inventive functionality of the claimed computer program will be explained in more detail in the following description in conjunction with the remaining figures illustrating the program flow. The detailed description which follows is represented largely in terms of processes and symbolic representations of operations by computer components.

Dynamic threat protection evolves disparate point solutions into an integrated prevention and protection system. Vulnerability assessment, firewall protection, protocol analysis to identify suspicious network traffic, virus blocking, application protection, behavioral analysis and protection policy updates all work as part of the same structure.

Each host shares critical security data with the other elements of the system. Pattern attacks that are difficult to detect by individual hosts become apparent once security is measured across the breadth of the system. Security policy preferably emanates from a centralized resource, which in turn handles data analysis and reporting for both technical and managerial oversight.

The overall protection system can be supported by global threat analysis and cutting-edge research. In other words, dynamic threat protection allows for real-time or near-real-time recognition of potential threats, and extremely rapid adjustment to changing security environments. Dynamic threat protection can recognize and adjust for new equipment or alterations in existing systems, networks, or hosts.

Dynamic threat protection can automatically learn how to work more effectively the longer it is in use. Dynamic threat protection searches for protection policies on networks, servers, hosts, and mobile systems. If none are found, security policies can be deployed from a central management environment and configured according to an enterprise-wide security policy. This part of the process can take place as part of a regularly scheduled assessment of the system, or on demand when new equipment is deployed.

Dynamic threat protection provides threat detection capabilities via protocol analysis, pattern matching, behavior analysis, and vulnerability assessment. Once all security policies are in place and have been verified as active and up to date, dynamic threat protection is ready to analyze the system, network, or hosts for vulnerabilities, both on demand and in response to suspicious activity occurring at the system, network, or host level. This vulnerability assessment is quickly parsed and analyzed at the host level, then passed up to the system environment for higher level correlation and analysis. In case of active attack, the exemplary system preferably has the capability to initiate appropriate investigative and defensive measures without direct administrator intervention, including the capability to block active attacks.

Dynamic threat protection assists traditionally independent security technologies to work together. Data collection, correlation and analysis capability break down into two separate components. The first, event correlation, is a real time, short term response in which the goal is to stop the event and limit the damage to the system, network, or host. The second, longer term component, threat correlation, uses information from a range of security events to assemble a recognizable threat pattern, then applies this knowledge across all systems, networks, and hosts as part of a basic risk assessment and remediation process.

Event correlation depends on network and host sensors capable of sorting through extensive device logs and intelligently escalating only the most relevant information to administrators. Threat correlation builds on the information parsed and processed at lower levels to recognize patterns and vulnerabilities that do not become apparent on a host-by-host basis. In either case, built-in analysis capabilities of dynamic threat protection reduce false positives, improve overall protection of the system, and help ensure business continuity.

Vulnerability assessment drives the dynamic threat protection process for two reasons: 1) discovery of what is actually part of the network; and 2) identification of what on the network might be vulnerable to attack or misuse. This information allows an enterprise to turn off unused services, identify and update protection policies on vulnerable software, and make educated decisions about which elements of the overall infrastructure require the most extensive protection measures. Once a decision is made to protect an element of the system, dynamic threat protection can determine whether to block the attack from entering the system or block elements of the system from receiving the attack while allowing the attack in to non-vulnerable elements. Furthermore, dynamic threat protection can determine how best to block the attack, whether it be actively, by preventing this and future attacks, or passively, by sending a signal to the attacker or the receiver ending this particular communication link.

Dynamic threat protection uses vulnerability assessment information to deliver basic event correlation. Threat correlation then comes about when the network and host sensors and the vulnerability assessment regimen work as part of an ongoing feedback. Information uncovered by vulnerability assessment helps set up significantly more effective prevention and protection processes, and allows the protection platform to route attack and misuse information back into the assessment process to ensure that successful attacks can't be repeated. This process takes place at the network, server, and host levels, and can be used to validate that any protection system is in place, up to date against the latest threats, and functioning properly.

Furthermore, all components of the dynamic threat protection system can receive protection policy updates to assist in defending against one or more new threats to the system, network, or hosts. These protection policy updates ensure that the dynamic threat protection system is up-to-date on the latest threats and security developments. Protection policy updates are preferably self-installing, and easily deployed from a central management system. The protection policy updates are an addition to and do not overwrite or modify prior protection policies, therefore limiting the need to shut down a system, network, or host in order to initiate the policy update. By adding instead of replacing protection policies, the dynamic threat protection system continues to have up-to-date protection policies while giving system administrators an opportunity to decide when to complete a complete system upgrade at a time when system downtime will not be detrimental to enterprise performance.

Referring now to the drawings, in which like numerals represent like elements throughout the several figures, aspects of the present invention and an exemplary operating environment of the implementation of the present invention will be described.

FIG. 1 is a block diagram illustrating an exemplary system level architecture for implementing a dynamic threat protection process in accordance with an exemplary embodiment of the present invention. Now referring to FIG. 1, the exemplary system 100 comprises an intranet 105, an Internet 110, a firewall 115, an intrusion protection system 155, a virtual private network (“VPN”) 165 and a partner 170. The firewall 115 is communicably attached via a distributed computer network to the intranet 105, Internet 110, and intrusion protection system 155. The Internet 110 is a worldwide system of computer networks, in which users from one computer may get information from a second computer, if the user has permission or the second computer is not properly protected. The firewall 115 is a set of related programs, located at a network gateway, that protects the resources of a private network from users from other networks.

The intranet 105 typically comprises a private network that is contained within an enterprise. The intranet 105 can contain interlinked local area networks and have access to a wide area network. The intranet 105 typically includes one or more gateways to the Internet 110. The intranet 105 is communicably attached via a distributed computer network to the firewall 115, the intrusion protection system 155, the VPN 165 and the partner 170. The intranet 105 comprises a vulnerability assessment component 140, a data collection and correlation component 142 and multiple hosts 120-130.

The vulnerability assessment component 140 is communicably attached via a distributed computer network to the data collection and correlation component 142 and multiple hosts 120-130. The vulnerability assessment component 140 receives packets of data from outside the intranet 105. Once received, the packets are evaluated and the vulnerability of the system is determined by the vulnerability assessment component 140. The vulnerability assessment component 140 can then generate a report detailing the system's vulnerability, which is sent to the data collection and correlation component 142.

The data collection and correlation component 142 comprises a database 145 and a data correlation component 150 and is communicably attached via a distributed computer network to the intrusion protection system 155, the vulnerability assessment component 140, and multiple hosts 120-130. In one exemplary embodiment the database 145 is a SQL server database capable of storing the vulnerability assessment reports generated by the vulnerability assessment component 140.

The data correlation component 150 distills raw threat data into prioritized actionable information. The information can be prioritized by the level of threat a data packet poses to the system 100. In one exemplary embodiment, the types of correlation completed by the data correlation component 150 includes: target, comparative, advanced analysis, and custom correlation. Asset correlation assesses events and incidents based on a prioritized view of an organization's protected assets, where the most valuable or crucial business assets take priority over lesser events. Comparative correlation compares anomalous network threat activity to known baselines and previous vulnerability assessments, helping to determine the enterprise's overall threat situation and risk exposure. Advanced analysis correlation allows a security administrator to select one or more events and conduct an in-depth analysis of the suspected attack. Custom correlation provides the security administrator with the ability to tailor intrusion protection defenses to meet enterprise specific needs.

The hosts 120-130 are communicably attached via a distributed computer network to the vulnerability assessment component 140 and the data collection and correlation component 142. A host can be any computer or electronic device having full two-way access to other computers or electronic devices on the intranet 105 or Internet 110. In one exemplary embodiment, a first host 120 is a desktop computer communicably attached to the intranet 105.

The VPN 165 is communicably attached via a distributed computer network to the intranet 105. The VPN 165 provides a method of using public telecommunications infrastructure to provide remote offices or individual users with a secure access to the enterprises computing network. The partner 170 is communicably attached via a distributed computer network to the intranet 105. The partner 170 represents one or more separate and distinct enterprises, other than the enterprise which owns the system 100, which has been given access to the system 100 based on the close working relationship between the enterprises. In one exemplary embodiment, the partner 170 is implemented by an extranet.

The intrusion protection system 155 is communicably attached via a distributed computer network to the Internet 110, the intranet 105, the firewall 115 and the data collection and correlation component 142. The intrusion protection system 155 comprises one or more network sensors 157 and a packet analysis component 160. The network sensor 157 is communicably attached via a distributed computer network to the packet analysis component 160 and the data collection and correlation component 142. The network sensor 157 receives instructions from the data correlation component 150 and either blocks packets of data or allows them to pass into the system 100 based on those instructions. The packet analysis component 160 contains data analysis programs to analyze network traffic on the system 100 to determine if the traffic is malicious. The packet analysis component 160 can also normalize network traffic to allow it to be analyzed. Furthermore, the packet analysis component 160 can reassemble traffic which enters the system 100 scrambled so that the traffic can be analyzed.

In one exemplary embodiment, a packet analysis component is located on each host 120-130. For an alternative exemplary embodiment, the system 100 has at least one intrusion protection system 155. The intrusion protection system 155 can be placed between the Internet 110 and the firewall 115 or between the firewall 115 and the intranet 105. In an alternative exemplary embodiment, the intrusion protection system 155 can be placed “in-line” with the intranet 105 and another network, such as the partner 170. In this alternative exemplary embodiment, the network connection to the intranet 105 can be blocked and every packet can be analyzed by the network sensors 157.

FIG. 2 is a block diagram illustrating an exemplary host 120 level architecture for implementing a dynamic threat protection process in accordance with an exemplary embodiment of the present invention. Now referring to FIG. 2, the exemplary host 120 comprises a scanning component 210, a host sensor 215, a local data correlation component 270 and a packet analysis component 160. The scanning component 210 is communicably attached to the local data correlation component 270 and the host sensor 215. The local data correlation 270 is communicably attached to the packet analysis component 160 and the scanning component 210. The packet analysis component 160 is communicably attached to the local data correlation component 270 and the host sensors 215.

The scanning component 210 receives the packet from the system 100, parses the packet header, determines the type of protocol used by the packet, and determines the host's 120 vulnerability to the packet. The scanning component passes this information along with the packet to the local data correlation component 270. The local data correlation component can modify the protection policy for the host 120 by evaluating the packet and the vulnerabilities of the host 120 and identifying blocking methods for reducing or eliminating those vulnerabilities. The packet analysis component 160 contains algorithms to analyze network traffic on the host 120 to determine if the traffic is malicious. The host sensor 215 receives instructions from the local data correlation component 270 and the packet analysis component 160 and either blocks packets of data or allows them to enter into the host 120 based on those instructions.

FIGS. 3-12 are logical flowchart diagrams illustrating the computer-implemented processes completed by an exemplary method for dynamically protecting an online business operation from attacks against its system, network and hosts. FIG. 3 is a logical flowchart diagram 300 presented to illustrate the general steps of an exemplary process for dynamically protecting a computer system within the representative operating environment of the system 100 of FIG. 1.

Now referring to FIGS. 1 and 3, the exemplary method 300 begins at the START step and proceeds to step 305, in which a policy is created for the system 100 by the data correlation component 150. In step 310, an inquiry is conducted to determine if the system 100 receives a packet from a source outside the system 100, such as the Internet 110. The packet is received at the network sensor 157 and typically contains a data stream and a packet header. If a packet is not received, the “NO” branch is followed to step 310. If a packet is received by the system 100, the “YES” branch is followed to step 315. In step 315, an inquiry is conducted to determine if the received packet should be blocked. If so, the “YES” branch is followed to step 325 for a further determination on how to block the received packet. If a decision is made to pass the packet, the “NO” branch is followed to step 340, where the data correlation component 150 allows the packet to enter the system 100. From step 340, the process returns to step 310. If the packet is blocked, the data correlation component 150 will not allow the packet to enter the system 100. The blocking determination typically occurs within the intrusion protection system 155.

In step 325, an inquiry is conducted to determine if the intrusion protection system 155 blocks the packet actively or passively. A packet is blocked passively by the system 100, network or host 120 sending a reset packet to either a host 120 or the party sending the packet. The party or host 120 receiving the reset packet is informed that the connection has been terminated. The party or host 120 could attempt to reconnect immediately after receiving the reset packet. A packet is blocked actively by the system 100, network or host 120 gathering network access information from the party sending the packet or its intended receiver or both and preventing packets from being received from a party having the same network access information. For example, the system 100 can determine the network address of the party sending the packet. The system 100 instructs the intrusion protection system 155 to allow any packets from the same network address to pass into the system 100 for a certain period of time. The time period can be short, or indefinite depending on user preferences.

If blocking is done passively, the “PASSIVE” branch is followed to step 330, where the packet is passively blocked. If the intrusion protection system 155 determines that the packet should be blocked actively, the “ACTIVE” branch is followed to step 335, where the packet is actively blocked. In one exemplary embodiment, packets received and analyzed at the system level 100 are blocked passively from the system 100. The process returns to step 310.

FIG. 4 is a logical flowchart diagram illustrating an exemplary computer-implemented method for the creation of a policy by the data correlation component 150 in the system 100 as completed by step 305 of FIG. 3. Referencing FIGS. 1 and 4, the exemplary method 305 begins with the vulnerability assessment component 140 assessing the system 100 for vulnerabilities to known attacks in step 405. An attack is a known attack if it has been used previously to attack this or other systems 100 and data is available to define the characteristics of the attack. In step 406, the vulnerability assessment component 140 creates a vulnerability assessment report based on the assessment. The vulnerability assessment component 140 sends the vulnerability assessment report to the database 145 in the data collection and correlation component 142 in step 407. In step 410, database 145 stores the vulnerability assessment report and makes it available to the data correlation component 150.

In step 415, the data correlation component 150 completes a correlation analysis of the data provided in the vulnerability assessment report against a set of known information about the system 100. The set of known information includes the system parameters, the software running on the system 100, the number and location of networks and hosts 120 with access to the system 100 and a prioritized order of protecting different areas of the system 100 from differing levels of attack. Correlation is the process of distilling raw threat data into prioritized actionable information. The object of a correlation analysis is to spot real threats to the system 100 immediately and minimize or eliminate false positives of non-threatening packets.

In step 420, an inquiry is conducted to determine if the system 100 is vulnerable to attacks based on the correlation analysis completed by the data correlation component 150. If not, the “NO” branch is followed to step 310 of FIG. 3. If the system 100 is vulnerable to attack, the “YES” branch is followed to step 425, where the data correlation component 150 creates a policy to stop attacks. The policy created by the data correlation component 150 is typically based on known vulnerabilities of the components of the system 100. In step 430, the data correlation component 150 sends the policy to the intrusion protection system 155, which distributes the policy to the network sensors 157. In step 435, the data correlation component 150 sends the policy to the host sensors 180. In one exemplary embodiment, each host, 120-130, contains a host sensor 180 at the host 120. The process then continues to step 310 of FIG. 3.

FIG. 5 is a logical flowchart diagram illustrating an exemplary computer-implemented method for determining whether to block a packet from entering a system 100 as completed by step 315 of FIG. 3. Referencing FIGS. 1, 2, and 5, the exemplary method 315 begins with the IPS 155, network sensor 157, or host sensor 210 receiving a packet in step 505. The component receiving the packet can depend on whether a system, network, or host is being protected. In step 510, an inquiry is conducted to determine if the packet contains characteristics which make it suspicious. A packet can contain suspicious characteristics if it resembles packets which have infected this or other systems 100, networks, or hosts 120 previously. The packet's signature can be analyzed to make this determination. Information retrieved from the packet analysis component 160 assists in determining if the packet contains suspicious characteristics. If the packet does not contain suspicious characteristics, the “NO” branch is followed to step 515, where another packet is received and the process returns to step 510. If the packet does contain suspicious characteristics, the “YES” branch is followed to step 520.

In step 520, an inquiry is conducted to determine if the packet should be discarded based on the determination that the packet contained suspicious characteristics. If so, the “YES” branch is followed to step 525, where the packet is blocked from the system 100, network, or host 120. If further analysis of the packet is necessary, or desired, the “NO” branch is followed to step 530, where the IP protocol of the packet is extracted from the packet header by the data correlation component 150, local data correlation component 270, or based on signature information in the packet header, depending on if the packet is received at the system 100, network, or host 120. In step 535, an inquiry is conducted to determine if the IP protocol in the packet header is a Transmission Control Protocol (“TCP protocol”). If so, the “YES” branch is followed to step 325 of FIG. 3. However, if the IP protocol is not a TCP protocol, the “NO” branch is followed to step 540. In step 540, an inquiry is conducted to determine if the IP protocol in the packet header is a User Datagram Protocol (“UDP protocol”). If so, the “YES” branch is followed to step 705 of FIG. 7. If the protocol is not a UDP protocol, then the “NO” branch is followed to step 545. In one exemplary embodiment, packets containing UDP protocols are only blocked actively. In step 545, an inquiry is conducted to determine if the IP protocol in the packet header is an Internet Control Message Protocol (“ICMP protocol”). If so, the “YES” branch is followed to step 805 of FIG. 8. However, if the IP protocol is not an ICMP protocol, then the “NO” branch is followed to step 340 of FIG. 3, where the packet is allowed to pass into the system 100. In one exemplary embodiment, packets containing ICMP protocols are only blocked actively by the host sensors 215.

FIG. 6 is a logical flowchart diagram illustrating an exemplary computer-implemented method for the intrusion protection system 155 or network sensors 157 passively blocking a packet as completed by step 330 of FIG. 3. Now referring to FIGS. 1, 2, and 6, the exemplary method 330 begins with an inquiry conducted to determine if the system 100 should reset the intruder in step 605. The intruder is the origination point from which the packet was received. If the intruder should be reset, the “YES” branch is followed to step 610, where the packet analysis component 160 sends a reset packet to the intruder. The reset packet indicates to the intruder that the conversation has been terminated by the system 100. The process continues to step 615. If the intruder should not be reset, the “NO” branch is followed to step 615.

In step 615, an inquiry is conducted to determine if the victim should be reset. The victim is the host 120, network, or system 100 which is receiving the packet. In one exemplary embodiment, the signature within the packet header determines whether to reset the intruder, the victim, or both. In another exemplary embodiment, the policy created by the data correlation component 150 or local data correlation component 270 or signature information in the packet header determines whether to reset the intruder, the victim, or both. If the victim is not reset, the “NO” branch is followed to step 310 of FIG. 3. On the other hand, if the victim should be reset, the “YES” branch is followed to step 620, where the network sensor 157 retrieves the victim's identification information. The identification information typically includes the Internet protocol address of the network or system 100. In step 625, the data correlation component 150 determines which victim(s) to reset based on the retrieved identification information and the known vulnerabilities of the system 100. A reset packet is sent to the victim system 100 in step 630. The reset packet instructs the victim to end the conversation with the intruder.

In step 635, an inquiry is conducted to determine if the victim(s) was the only party that was sent a reset packet. If so, the “YES” branch is followed to step 640, where packet received from the intruder is not blocked. The process continues to step 310 of FIG. 3. If both the victim(s) and the intruder were sent reset packets, the “NO” branch is followed to step 310 of FIG. 3.

FIG. 7 is a logical flowchart diagram illustrating an exemplary computer-implemented method for host sensors 215 actively blocking packets containing TCP or UDP protocols at the host 120 as completed by step 335 of FIG. 3. Referencing FIGS. 1, 2, and 7, the exemplary method 335 begins with an inquiry to determine if the block rule used to block the packet is valid or expired in step 705. Rules for blocking a packet are typically stored in the packet analysis component 160. In one exemplary embodiment, the rules can have a lifetime, or period which they will be applied, after which, the rule is considered expired and no longer enforced. If the rule is expired, the “EXPIRED” branch is followed to step 310 of FIG. 3, where an inquiry is conducted to determine if another packet is received at the host 120. If the rule is not expired, the “VALID” branch is followed to step 710.

In step 710, an inquiry is conducted to determine if the intruder's Internet protocol address (“IP address”) should be blocked from the system 100. The determination is typically made by the data correlation component 150, the local data correlation component 270, or based on signature information in the packet header. If the intruder IP address should be blocked, the “YES” branch is followed to step 715, where an instruction to block the intruder's IP address is added to a TCP-UDP block criteria in the packet analysis component 160. The process continues to step 720. If the intruder IP address should not be blocked, the “NO” branch is followed to step 720. In step 720, an inquiry is conducted to determine if the intruder's port should be blocked from the system 100. The determination is typically made by the data correlation component 150, the local data correlation component 270, or based on signature information in the packet header. If the intruder's port should be blocked, the “YES” branch is followed to step 725, where an instruction to block the intruder's port as well as the number of the intruder's port is added to the TCP-UDP block criteria. The process continues to step 730. If the intruder's port should not be blocked, the “NO” branch is followed to step 730.

In step 730, an inquiry is conducted to determine if the victim's IP address should be blocked from the system 100. The determination is typically made by the data correlation component 150, the local data correlation component 270, or based on signature information in the packet header. The victim typically includes a host 120. Blocking the host's 120 IP address from the system 100 would isolate the host 120 from the rest of the system 100 or network. The host 120 may have unique vulnerabilities which make it easier to isolate the host rather than block the intruder from the entire system 100 or fix the system 100 as a whole. In one exemplary embodiment, the host 120 is isolated from the system if the host 120 is not currently in use, or does not need access to the system 100 in order to function properly. If the victim's IP address should be blocked from the system 100, the “YES” branch is followed to step 1035, where an instruction containing the victim's IP address is added to the TCP-UDP block criteria. The process continues to step 740. If the victim's IP address should not be blocked, the “NO” branch is followed to step 740.

In step 740, an inquiry is conducted to determine if the victim's IP port should be blocked from the system 100. The determination is typically made by the data correlation component 150, the local data correlation component 270, or based on signature information in the packet header. If so, the “YES” branch is followed to step 745, where an instruction containing the victim's IP port is added to the TCP-UDP block criteria in the packet analysis component 160. The process continues to step 750. If the victim's port should not be blocked, the “NO” branch is followed to step 750, where an inquiry is conducted to determine if a block percentage is met. The block percentage is a numerical value in the data correlation component 150 or the local data correlation component 270 that evaluates the number of packets being blocked as compared to the total number of packets received by the system 100 or the host 120. If the numerical value is reached, or met, then the packet currently being evaluated is blocked from the host 120 and system 100. If the block percentage has been met, the “YES” branch is followed to step 755, where an instruction that the block percentage has been met is added to the TCP-UDP block criteria. The process continues to step 760. If the block percentage has not been met, the “NO” branch is followed to step 760, where the host sensor 215 applies the TCP-UDP block criteria to the received packet. The process continues to step 310 of FIG. 3.

FIG. 8 is a logical flowchart diagram illustrating an alternative exemplary computer-implemented method for host sensors 215 actively blocking packets containing ICMP protocol at the host 120 as completed by step 335 of FIG. 3. Referencing FIGS. 1, 2, and 8, the alternative exemplary method 335 a begins with an inquiry to determine if the block rule used to block the packet is valid or expired in step 805. Rules for blocking a packet are typically stored in the packet analysis component 160. If the rule is expired, the “EXPIRED” branch is followed to step 310 of FIG. 3, where an inquiry is conducted to determine if another packet is received at the host 120. If the rule is not expired, the “VALID” branch is followed to step 810.

In step 810, an inquiry is conducted to determine if the intruder's IP address should be blocked from the system 100. The determination is typically made by the data correlation component 150, the local data correlation component 270, or based on signature information in the packet header. If the intruder IP address should be blocked, the “YES” branch is followed to step 815, where an instruction to block the intruder's IP address is added to an ICMP block criteria in the packet analysis component 160. The process continues to step 820. If the intruder's IP address should not be blocked, the “NO” branch is followed to step 820. In step 820, an inquiry is conducted to determine if the victim's IP address should be blocked from the system 100. The determination is typically made by the data correlation component 150, the local data correlation component 270, or based on signature information in the packet header. The victim typically includes a host 120. Blocking the host's 120 IP address from the system 100 would isolate the host 120 from the rest of the system 100 or network. If the victim's IP address should be blocked from the system 100, the “YES” branch is followed to step 825, where an instruction containing the victim's IP address is added to the ICMP block criteria. The process continues to step 830. If the victim's IP address should not be blocked, the “NO” branch is followed to step 830.

In step 830, an inquiry is conducted to determine if the packet ICMP code should be blocked from the system 100. The determination is typically made by the data correlation component 150, the local data correlation component 270, or signature information in the packet header. If packet ICMP code should be blocked, the “YES” branch is followed to step 835, where an ICMP code field is added to the ICMP block criteria. The process continues to step 840. If ICMP code should not be blocked, the “NO” branch is followed to step 840. In step 840, an inquiry is conducted to determine if the victim's ICMP type should be blocked from the system 100. If so, the “YES” branch is followed to step 845, where the victim's ICMP type is added to the ICMP block criteria in the packet analysis component 160. The process continues to step 850. If the victim's ICMP type should not be blocked, the “NO” branch is followed to step 850. The determination is typically made by the data correlation component 150, the local data correlation component 270, or signature information in the packet header.

In step 850, an inquiry is conducted to determine if a block percentage for ICMP packets has been met. If the block percentage is reached, or met, then the packet currently being evaluated is blocked from the host 120 and system 100. If the block percentage has been met, the “YES” branch is followed to step 855, where an instruction that the block percentage has been met is added to the ICMP block criteria. The process continues to step 860. If the block percentage has not been met, the “NO” branch is followed to step 860, where the host sensor 215 applies the ICMP block criteria to the received packet. The process continues to step 310 of FIG. 3.

FIG. 9 is a logical flowchart diagram 900 presented to illustrate the general steps of an exemplary computer-implemented method for dynamically protecting a host 120 of FIG. 2. Now referring to FIGS. 2 and 9, the exemplary method 900 begins at the START step and proceeds to step 905, in which the host 120 is configured with a policy based on a user's desired security level. Policy configuration is typically determined by the user of the host 120 selecting a risk aversion setting. In one exemplary embodiment four risk aversion settings exist: trusting, cautious, nervous, or paranoid.

When a user selects the “trusting” risk aversion setting the host 120 usually will not block any packet streams received or sent by the host 120. The “cautious” setting blocks unsolicited network traffic attempting to access operating system and networking services. The “cautious” setting is good for regular use on the Internet 110. Selecting the “nervous” setting blocks all unsolicited packets received at the system 100 except for some interactive content on web sites. The nervous setting is preferable if the system 100 is experiencing frequent attacks. Selecting the “paranoid” setting blocks all packet streams received, but allows packets to be sent from the host 120. The “paranoid” setting is often used when a system 100 is undergoing continuous repeated attacks.

In step 910, the policy is sent to the host sensor 215. The policy typically contains the blocking protocol for the host 120. In step 915, an inquiry is conducted to determine if the host 120 receives a packet stream. If not, the “NO” branch is followed to step 915. If the host 120 receives a packet stream, the “YES” branch is followed to step 920. The host 120 typically receives packets from the system 100, the network, and the Internet 110. In step 920, the packet is analyzed by a scanning component 210 and the local data correlation component 270. In step 925 and inquiry is conducted to determine if the packet stream should be blocked at the host 120. If not, the “NO” branch is followed to step 955, where the packet stream is allowed to pass through to the host 120. The process then continues to step 915. However, if the packet should be blocked, the “YES” branch is followed to step 940. In one exemplary embodiment, the inquiry conducted in step 925 is the same as the inquiry conducted in step 315 of FIG. 3.

In step 940, an inquiry is conducted to determine if the packet should be blocked actively or passively. If the packet will be blocked passively, the “PASSIVE” branch is followed to step 945, where the host sensor 215 passively blocks the packet. In one exemplary embodiment, the steps for passively blocking a packet at the host 120 are the same as step 330 of FIG. 3. The process then returns to the step 915. If the packet will be blocked actively, the “ACTIVE” branch is followed to step 950, where the host sensor 220 actively blocks the packet. In one exemplary embodiment, the steps for actively blocking a packet at the host 120 are the same as step 335 of FIG. 3. In another exemplary embodiment, all packets received at the host 120 are actively blocked by the host sensors 215. The process then returns to step 915.

FIG. 10 is a logical flowchart diagram illustrating an exemplary computer-implemented method for scanning a packet stream at the host level as completed by step 920 of FIG. 9. Referencing FIGS. 1, 2, and 9, the exemplary method 920 begins with the scanning component 210 scanning the received packet stream in step 1005. In step 1007, an inquiry is conducted to determine if the scanning component 210 detects an event in the packet. An event includes data within a packet which the host 120 may be vulnerable to if the packet is allowed to pass into the host 120. If an event is not detected, the “NO” branch is followed to step 925 of FIG. 9. If an event is detected, the “YES” branch is followed to step 1020, where the scanning component 210 generates a vulnerability assessment report based on a detected event in the packet, for the host 120. The scanning component 210 sends the vulnerability assessment report to the local data correlation component 270 in step 1025.

In step 1030, the local data correlation component 270 corrects the host's 120 vulnerability to the detected event. By correcting the vulnerability, the host 120 will no longer be vulnerable to the same kind of event. In step 1035, the local data correlation component 270 generates a policy to scan for the detected event. The process continues to step 925 of FIG. 9.

FIG. 11 is a logical flowchart diagram 1100 presented to illustrate the general steps of an exemplary computer-implemented method for dynamically protecting a network. Now referring to FIGS. 1 and 11, the exemplary method 1100 begins at the START step and proceeds to step 1105 where a manager program creates a policy for protecting the network. In step 1110, the manager program sends the policy to one or more network sensors 157. In step 1115, an inquiry is conducted to determine if a packet is received by the network. If not, the “NO” branch is followed to step 1115. However, if a packet is received by the network, the “YES” branch is followed to step 1120. In step 1120, the network sensor 157 which received the packet processes it.

In step 1125, an inquiry is conducted to determine if the network contains a data correlation component 150. The data correlation component 150 is an optional component of the network. If the network contains a data correlation component 150, the “YES” branch is followed to step 1130, where the data correlation component 150 correlates the data in the packet. In step 1130, the data correlation component creates an updated policy based on the data correlation component's 150 evaluation of the packet and the vulnerabilities of the network. The process continues to step 1140. If the network does not contain a data correlation component, the “NO” branch is followed to step 1140.

In step 1140, an inquiry is conducted to determine if the packet should be blocked. If not, the “NO” branch is followed to step 1150, where the packet is allowed to pass into the network. The process then returns to step 1115. If the packet should be blocked, the “YES” branch is followed to step 1145. In one exemplary embodiment the inquiry of step 1140 is the same as the inquiry of step 315 of FIG. 3. In step 1145, an inquiry is conducted to determine if the network sensor 157 should block the packet actively or passively. If the packet should be blocked passively, the “PASSIVE” branch is followed to step 1155, where the network sensor 157 blocks the packet passively from the network. The process then returns to step 1115. In one exemplary embodiment, the steps for passively blocking a packet at the host 120 are the same as step 330 of FIG. 3. On the other hand, if the packet should be blocked actively, the “ACTIVE” branch is followed to step 1160, where the network sensor 157 blocks the packet actively from the network. The process then returns to step 1115. In one exemplary embodiment, the steps for actively blocking a packet at the host 120 are the same as step 335 of FIG. 3.

FIG. 12 is a logical flowchart diagram 1200 illustrating an exemplary computer-implemented method for updating a protection policy for a system 100, network or host 120. Now referring to FIGS. 1, 2, and 12, the exemplary method 1200 begins at the START step and proceeds to step 1205, where an inquiry is conducted to determine if the system 100, network, or host 120 receives a new policy at the packet analysis component 160. The data correlation component 150 searches for protection policies on the server 100, network, or host 120. If no protection policies are found to deal with the attack, a new security policy is deployed from a central management environment to the packet analysis component 160. The new policy does not replace any previous protection policy in the host 120, but instead, provides at least one new program to assist in blocking attacks. The new protection policy self-installs in the host 120. The new protection policy ensures that the protection system is up-to-date on the latest threats and security developments. Furthermore, by providing additional protection policies instead of modifying prior protection policies, the system 100 does not require downtime. Thus, a system administrator can delay initiating a complete protection system upgrade until system 100 downtime will be less detrimental to enterprise performance. In one exemplary embodiment, the new policy is sent to the packet analysis component 160 via the Internet 110 from a third-party. If a new policy is not received, the “NO” branch is followed to step 1205, where the inquiry is conducted again. If a new policy is received, the “YES” branch is followed to step 1210.

In step 1210, the packet analysis component 160 delivers the new policy to the host 120. In step 1215, the host 120 parses the new policy. Parsing allows the host 120 to separate the multiple programs which may be contained in the new policy. In step 1220, the new protection policy added to the host 120, is reconfigured by the local data correlation component 270 based on the risk aversion setting at the host 120. In one exemplary embodiment, the policy configured at the host 120 includes the new policy, as well as previous policies received by the host 120. The host 120 sends the reconfigured policy to the host sensors 215 in step 1225. The process returns to step 1205 to determine if another new policy has been received by the packet analysis component.

In conclusion, the present invention supports a computer-implemented method and system for determining if a system, network, or host is vulnerable to a particular type of attack from data received from an outside source. If the system, network, or host is vulnerable, the present invention can determine one or more methods for blocking the data packet from passing into the system, network, or host determined to be vulnerable, while allowing the data packet to pass into the system, network, or host which is not vulnerable. Furthermore, the present invention supports correlating suspicious data packets received by a computer system against hosts with may be vulnerable to a particular type of attack to support the blocking of data packets for the vulnerable hosts. Additionally, the present invention supports a method an system for updating policies used by the system, network, or host to support the blocking of data packets from the vulnerable hosts.

It will be appreciated that the present invention fulfills the needs of the prior art described herein and meets the above-stated objectives. While there have been shown and described several exemplary embodiments of the present invention, it will be evident to those skilled in the art that various modifications and changes may be made thereto without departing from the spirit and the scope of the present invention as set forth in the appended claims and equivalence thereof. 

We claim:
 1. A method for generating a policy to protect a computer system from intrusions, the method comprising the steps of: a computer determining vulnerabilities of the computer system based on a comparison to a plurality of known attacks; responsive to determining that the computer system is vulnerable to the plurality of known attacks, the computer generating a report comprising data detailing the computer systems vulnerabilities and identifying one or more components of the computer system that is vulnerable to the plurality of known attacks; the computer correlating the data in the report to at least one of a prioritized order of protecting different areas of the computer system from different attacks and a range of security events to generate a threat pattern; the computer determining if the computer system is vulnerable to an attack associated with the threat pattern; and responsive to determining that the computer system is vulnerable to the attack, the computer generating the policy comprising a protocol to block suspicious data packets to protect the computer system from the attack based on a predetermined level of security associated with the computer system.
 2. The method of claim 1, wherein the known attack comprises an attack that has been previously used to attack the computer system.
 3. The method of claim 1, wherein the known attack comprises an attack that has been previously used to attack another computer system.
 4. The method of claim 1, wherein correlating comprises processing the data from the vulnerability assessment report to generate a prioritized listing of a level of threats that a data packet poses to the computer system.
 5. The method of claim 1, wherein correlation comprises a comparative correlation analysis operable to compare a network threat activity to a known baseline.
 6. The method of claim 1, wherein policy comprises a set of instructions to identify data packets that are to be blocked to protect the computer system from the attack.
 7. The method of claim 1: wherein the policy is periodically updated to ensure that the protection of the computer system is up to date on the latest threats, previously known threats and unknown attacks, and wherein the policy updates are installed as an addition to an existing policy to avoid shut down of the computer system for updating the policy.
 8. A computer program product for generating a policy to protect a computer system from intrusions, the computer program product comprising: one or more computer-readable tangible storage devices and program instructions stored on at least one of the one or more storage devices, the program instructions comprising: program instructions to determine vulnerabilities of the computer system based on a comparison to a plurality of known attacks; program instructions, responsive to determining that the computer system is vulnerable to the plurality of known attacks, to generate a report comprising data detailing the computer systems vulnerabilities and identifying one or more components of the computer system that is vulnerable to the plurality of known attacks program instructions to correlate the data in the report to at least one of a prioritized order of protecting different areas of the computer system from different attacks and a range of security events to generate a threat pattern; program instructions to determine if the computer system is vulnerable to an attack associated with the threat pattern; and program instructions, responsive to determining that the computer system is vulnerable to the attack, to generate the policy comprising a protocol to block suspicious data packets to protect the computer system from the attack based on a predetermined level of security associated with the computer system.
 9. The method of claim 8, wherein the known attack comprises an attack that has been previously used to attack the computer system.
 10. The method of claim 8, wherein the known attack comprises an attack that has been previously used to attack another computer system.
 11. The method of claim 8, wherein correlating comprises processing the data from the vulnerability assessment report to generate a prioritized listing of a level of threats that a data packet poses to the computer system.
 12. The method of claim 8, wherein correlation comprises a comparative correlation analysis operable to compare a network threat activity to a known baseline.
 13. The method of claim 8, wherein policy comprises a set of instructions to identify data packets that are to be blocked to protect the computer system from the attack.
 14. The method of claim 8: wherein the policy is periodically updated to ensure that the protection of the computer system is up to date on the latest threats, previously known threats and unknown attacks, and wherein the policy updates are installed as an addition to an existing policy to avoid shut down of the computer system for updating the policy.
 15. A computer system for generating a policy to protect one or more computers from intrusions, the computer system comprising: one or more first processors, one or more first computer-readable memories, one or more computer-readable tangible storage devices, and program instructions stored on at least one of the one or more first storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, the program instructions comprising: program instructions to determine vulnerabilities of the computer system based on a comparison to a plurality of known attacks; program instructions, responsive to determining that the computer system is vulnerable to the plurality of known attacks, to generate a report comprising data detailing the computer systems vulnerabilities and identifying one or more components of the computer system that is vulnerable to the plurality of known attacks; program instructions to correlate the data in the report to at least one of a prioritized order of protecting different areas of the computer system from different attacks and a range of security events to generate a threat pattern; program instructions to determine if the computer system is vulnerable to an attack associated with the threat pattern; and program instructions, responsive to determining that the computer system is vulnerable to the attack, to generate the policy comprising a protocol to block suspicious data packets to protect the computer system from the attack based on a predetermined level of security associated with the computer system.
 16. The method of claim 15, wherein the known attack comprises an attack that has been previously used to attack the computer system.
 17. The method of claim 15, wherein the known attack comprises an attack that has been previously used to attack another computer system.
 18. The method of claim 15, wherein correlating comprises processing the data from the vulnerability assessment report to generate a prioritized listing of a level of threats that a data packet poses to the computer system.
 19. The method of claim 15, wherein correlation comprises a comparative correlation analysis operable to compare a network threat activity to a known baseline.
 20. The method of claim 15, wherein policy comprises a set of instructions to identify data packets that are to be blocked to protect the computer system from the attack. 